this section competes a bit with Implementing Nosto
is it a general intro section?
Also it is quite flat without any nesting

Hey Timo, understand what you mean and I see there's some overlap but for now imo this is fine.

One main idea/background of the getting started guide is to use it in pre-sales. We want to set the expectations of the needed work and give a high level overview of what Nosto does etc., too often we had "mis-scopes" in the past. So we'd like to keep this guide separate from the main documentation to drive the narrative "read the full 'getting started guide' before our tech call".

How would you nest those pages? We tried to keep the structure as linear as possible, so as of now I can think of adding numbers for the menu to make this more clear, curious about your suggestions though, wdyt?

If it's pre-sales guide then it should be maybe named differently.
The whole "Implementing Nosto" section is also a getting started guide.

Maybe just a line at the very beginning of the section "Welcome & Support" that makes it clear that this is a guide which is meant for agencies that are implementing Nosto for clients.

We want the first page of our docs to be the getting started/quick start guide. Readers (inhouse devs or agencies) have 0 context of Nosto and therefore need an overview of our docs and guidance through the different aspects of an implementation. They will read it in two situations:

1. During pre-sales phase to make their estimate.
2. When starting implementing Nosto (can be later down the road and can also be by a person that wasn't involved in the pre-sales discussion)

Of course, the details can vary and they are covered in the next "chapters" of the documentation.

I agree that there are certain aspects that are overlapping, imo the current "introduction" page can be deleted as it is getting replaced by the entire "getting started" chapter with the subpages and updated checklists rather than paragraphs.

What do you think of keeping the naming and removing https://github.com/Nosto/wiki-docs/blob/Techdocs/README.md (better said replacing it with https://github.com/Nosto/wiki-docs/blob/getting-started-guide-psn-and-headless/getting-started/README.md and maybe changing the headline "Welcome Guide")? @DJ-techie @timowestnosto

We want the first page of our docs to be the getting started/quick start guide. Readers (inhouse devs or agencies) have 0 context of Nosto and therefore need an overview of our docs and guidance through the different aspects of an implementation. They will read it in two situations:

1. During pre-sales phase to make their estimate.
2. When starting implementing Nosto (can be later down the road and can also be by a person that wasn't involved in the pre-sales discussion)

Of course, the details can vary and they are covered in the next "chapters" of the documentation.

I agree that there are certain aspects that are overlapping, imo the current "introduction" page can be deleted as it is getting replaced by the entire "getting started" chapter with the subpages and updated checklists rather than paragraphs.

What do you think of keeping the naming and removing https://github.com/Nosto/wiki-docs/blob/Techdocs/README.md (better said replacing it with https://github.com/Nosto/wiki-docs/blob/getting-started-guide-psn-and-headless/getting-started/README.md and maybe changing the headline "Welcome Guide")? @DJ-techie @timowestnosto